Warp wrote:
> 
>   I personally still think that it would be better to first get
> accustomed with programming (that is, you don't need to search in a book
> what was the syntax of a function or a for-loop) and get some experience
> before trying to handle a huge program. Better start with small programs
> (like a program which prints all prime numbers between 1 and 1000 and such),
> then write a bit bigger ones before even trying to patch a huge program.
> It will save a lot of time in the long run and the patch will probably be
> much better and efficient. If you start coding the patch from the scratch,
> with no experience at all, you'll probably make things in 50 lines which
> could be made in 5 lines much more efficiently and with a lot less trouble and
> work.

Therefore i suggested studying things before.  I never learned programming
systematically (apart from some Basic at school) and i think i learned
most about programming by studying others' code.  Some things of course
also require reading of books, but IMO that is usually an automatic
reaction when looking at the code and not understanding things (unless
there are some friendly Povers in range you can ask :-)

Learning programming systematically by reading books and doing programming
exercises is of course not bad either, but it can be quite frustrating and
it does not train you to understand code written by others.  

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message